I wrote $$. will fix later don't merge

Is there a chance that #861 will be included as well?

Hi!

Thanks a lot for the work and catching and fixing #884 so quickly ... do you have any estimate for the release of 5.5.1?

Is there a chance that #861 will be included as well?

@mjbogusz no, since it would require major release rather than just a patch release - #861 introduces a breaking change.

There is an open issue which tracks what needs to be done before a major release: #871 (it has #861 included in there)

@Andrew-Chen-Wang can we also include #894 in a release - it adds no-op migrations that are needed because Meta attribute of the models were updated?

@Andrew-Chen-Wang any chance we can do a release?

I have seen that there is a duplicate issue opened, and it has been recently fixed: #900, so to prevent similar issue opening, maybe we can do a release soon :)

hey guys, any update on this release?

@vgrozdanic With the risk of spamming, any updates on this?

@vgrozdanic With the risk of spamming, any updates on this?

@robertalexa sorry i have missed previous comment.

Only @Andrew-Chen-Wang from active maintainers has permissions to do releases. I have just merged one last change for 5.5.1, so when Andrew will have time i think we are good to release :)

Hi all, any updates on 5.5.1 release? Particularly for #831
We have been holding pyjwt upgrade for a while..

Hi folks, super sorry for the delay. @vgrozdanic what additional PRs need to be merged? if none, let me know if we should just make a release based on this PR! Feel free to directly edit this branch as well. I'll block out some time next weekend to look to release.

Hi all, any updates on 5.5.1 release? Particularly for #831 We have been holding pyjwt upgrade for a while..

@hakan-77 regarding the #831 we will release the fix for it in the next major version (6.0.0) which will go after 5.5.1 is released. Most of the work has already been done to address this, but will only be merged after we release 5.5.1

Hi folks, super sorry for the delay. @vgrozdanic what additional PRs need to be merged? if none, let me know if we should just make a release based on this PR! Feel free to directly edit this branch as well. I'll block out some time next weekend to look to release.

@Andrew-Chen-Wang awesome! Everything is already merged, i have updated the changelog with 2 more PRs that were merged after you opened this PR.

There's one more thing i am not sure about, and that is how to include the disclaimer for users who by accident generated a migration for this app (we can maybe c/p it from this comment: #894 (comment)). So far there has been no such case in the changelog, and not sure how you would want to include it.